Repository navigation
fix: upgrade Go toolchain to 1.27.2 for GO-2026-6608-stdlib - #3613
Closed
chainloop-platform[bot] wants to merge 1 commit into
Closed
chainloop-platform[bot] wants to merge 1 commit into
chainloop-platform[bot] wants to merge 1 commit into
Conversation
Contributor
Author
AI Session Checks —
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumped the repository Go toolchain declarations and release builder image pins from 1.27.1 to 1.27.2 so Chainloop no longer builds against the vulnerable stdlib release.
Vulnerability Fixed
GO-2026-6608-stdlib, HIGH: parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes.
Changes Made
go.modfromgo 1.27.1togo 1.27.2so the main module targets the patched Go release.app/controlplane/Dockerfile.goreleaser,app/cli/Dockerfile.goreleaser, andapp/artifact-cas/Dockerfile.goreleaserfromgolang:1.27.1@sha256:1e93e00a31255c07e9a34c4207f3006e1501730c5323697cee7dfb827fdae44ctogolang:1.27.2@sha256:007a316059246276cb214df93950be77837545dc78007a73e0291a4963d5d3bfso release builds use the patched stdlib.Verification
Ran
grype golang:1.27.2@sha256:007a316059246276cb214df93950be77837545dc78007a73e0291a4963d5d3bf --only-fixed -o jsonagainst the updated builder image digest and confirmedGO-2026-6608/CVE-2026-94440are absent; the scan returned zero matches. Also ransyft dir:. -o cyclonedx-json=sbom.json && grype sbom:sbom.json --only-fixed -o jsonin the patched repository, and the target advisory was not reported there either. Outcome: resolved.Risk Assessment
View the risk assessment in Chainloop